Improve gcov coverage reporting logic (and other minor changes) #766
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
covrep
make target didn't work quite right for client projects.Description of changes
README.md
with better descriptions of published Draco components. Also Update the copyright block and author list to reflect changes introduced with the release of Draco-7_5_0.compilerEnv.cmake
, update logic related to how thecovrep
target is created by allowing client projects to append toCODE_COVERAGE_IGNORE_REGEX
. Also use the newblock_indent
cmake function to pring this value when generating a build tree withCODE_COVERAGE=ON
.string_manip.cmake
provide a new cmake functionblock_indent
to make it easier to print formatted information when configuring a project.vendor_libraries.cmake
, to ensure that Draco's code coverage setup is called during project configuration. Also ensure that we search for the CUDA compiler.StackTrace
and associated unit test.Status